Compatibility Mechanisms for Devices in a Continuous Analyte Monitoring System and Methods Thereof

ABSTRACT

Methods, devices, and kits are provided for determining a compatibility of one or more devices in an analyte monitoring system.

RELATED APPLICATION

This application claims priority to U.S. provisional application No. 61/563,517, filed Nov. 23, 2011, entitled “Compatibility Mechanisms for Devices in a Continuous Analyte Monitoring System and Methods Thereof”, the disclosure of which is incorporated herein by reference in its entirety for all purposes.

BACKGROUND

The detection of the level of glucose or other analytes, such as lactate, oxygen or the like, in certain individuals is vitally important to their health. For example, the monitoring of glucose is particularly important to individuals with diabetes. Diabetics may need to monitor glucose levels to determine when insulin is needed to reduce glucose levels in their bodies or when additional glucose is needed to raise the level of glucose in their bodies.

Devices have been developed for continuous or automatic monitoring of analytes, such as glucose, in bodily fluid such as in the blood stream or in interstitial fluid. Some of these analyte measuring devices are configured so that at least a portion of the devices are positioned below a skin surface of a user, e.g., in a blood vessel or in the subcutaneous tissue of a user.

SUMMARY

Embodiments of the present disclosure include computer-implemented methods for determining a compatibility of one or more devices in an analyte monitoring system. Certain aspects include receiving identification code data related to a configuration of a first device, retrieving information including a predetermined list of one or more acceptable identification code data that is related to one or more first device configurations that are compatible with the analyte monitoring system, comparing the received identification code data with the one or more acceptable identification codes from the retrieved predetermined list and determining if the configuration of the first device is compatible with the analyte monitoring system based upon the received identification code data being identified in the predetermined list of acceptable identification code data.

Embodiments of the present disclosure include computer-implemented methods for determining a compatibility of one or more devices in an analyte monitoring system. Certain aspects include receiving identification code data related to a configuration of a first device, retrieving information including a predetermined list of one or more identification codes that are related to one or more first device configurations and one or more software functions relating to the one or more first device configurations, comparing the received identification code data with the one or more identification codes and determining an appropriate software function for processing analyte data obtained by the first device that is related to an analyte level of a user based upon a stored software function that corresponds to the received identification code data.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a data monitoring and management system such as, for example, an analyte (e.g., glucose) monitoring system in accordance with certain embodiments of the present disclosure;

FIG. 2 illustrates a data monitoring and management system for real time glucose measurement data acquisition and processing in one aspect of the present disclosure;

FIG. 3 is a block diagram of a receiver/monitor unit such as that shown in FIG. 1 in accordance with certain embodiments;

FIG. 4 is a flowchart illustrating a method for determining a compatibility of one or more devices in an analyte monitoring system in accordance with certain embodiments of the present disclosure;

FIG. 5 is a flowchart illustrating a method for determining a compatibility of one or more devices in an analyte monitoring system in accordance with certain embodiments of the present disclosure; and

FIG. 6 is a flowchart illustrating a method for determining a compatibility of one or more devices in an analyte monitoring system in accordance with certain embodiments of the present disclosure.

DETAILED DESCRIPTION

Before the present disclosure is further described, it is to be understood that this disclosure is not limited to particular embodiments described, as such may, of course, vary. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting, since the scope of the present disclosure will be limited only by the appended claims.

As will be apparent to those of skill in the art upon reading this disclosure, each of the individual embodiments described and illustrated herein has discrete components and features which may be readily separated from or combined with the features of any of the other several embodiments without departing from the scope or spirit of the present disclosure.

Where a range of values is provided, it is understood that each intervening value, to the tenth of the unit of the lower limit unless the context clearly dictates otherwise, between the upper and lower limit of that range and any other stated or intervening value in that stated range, is encompassed within the disclosure. The upper and lower limits of these smaller ranges may independently be included in the smaller ranges, and are also encompassed within the disclosure, subject to any specifically excluded limit in the stated range. Where the stated range includes one or both of the limits, ranges excluding either or both of those included limits are also included in the disclosure.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. Although many methods and materials similar or equivalent to those described herein can also be used in the practice or testing of the present disclosure, exemplary methods and materials are now described. All publications mentioned herein are incorporated herein by reference to disclose and describe the methods and/or materials in connection with which the publications are cited.

As used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. It is further noted that the claims may be drafted to exclude any optional element. As such, this statement is intended to serve as antecedent basis for use of such exclusive terminology as “solely,” “only” and the like in connection with the recitation of claim elements, or use of a “negative” limitation.

The publications discussed herein are provided solely for their disclosure prior to the filing date of the present application. Nothing herein is to be construed as an admission that the present disclosure is not entitled to antedate such publication by virtue of prior disclosure. Further, the dates of publication provided may be different from the actual publication dates which may need to be independently confirmed.

FIG. 1 shows a data monitoring and management system such as, for example, an analyte (e.g., glucose) monitoring system in accordance with certain embodiments of the present disclosure. Embodiments of the subject disclosure are described primarily with respect to glucose monitoring devices and systems, and methods of using two or more devices in a glucose monitoring system to determine the compatibility of one or more devices in the glucose monitoring system.

Analytes that may be monitored include, but are not limited to, acetyl choline, amylase, bilirubin, cholesterol, chorionic gonadotropin, creatine kinase (e.g., CK-MB), creatine, DNA, fructosamine, glucose, glutamine, growth hormones, hormones, ketones, lactate, peroxide, prostate-specific antigen, prothrombin, RNA, thyroid stimulating hormone, and troponin. The concentration of drugs, such as, for example, antibiotics (e.g., gentamicin, vancomycin, and the like), digitoxin, digoxin, drugs of abuse, theophylline, and warfarin, may also be monitored. In those embodiments that monitor more than one analyte, the analytes may be monitored at the same or different times.

Referring to FIG. 1, the analyte monitoring system 100 includes a sensor 101, a data processing unit (e.g., sensor electronics) 102 connectable to the sensor 101, and a primary receiver unit 104 which is configured to communicate with the data processing unit 102 via a communication link 103. In aspects of the present disclosure, the sensor 101 and the data processing unit (sensor electronics) 102 may be configured as a single integrated assembly 110. In certain embodiments, the integrated sensor and sensor electronics assembly 110 may be configured as an on-body patch device. In such embodiments, the on-body patch device may be configured for, for example, RFID or RF communication with a reader device/receiver unit, and/or an insulin pump.

In certain embodiments, the primary receiver unit 104 may be further configured to transmit data to a data processing terminal 105 to evaluate or otherwise process or format data received by the primary receiver unit 104. The data processing terminal 105 may be configured to receive data directly from the data processing unit 102 via a communication link which may optionally be configured for bi-directional communication. Further, the data processing unit 102 may include a transmitter or a transceiver to transmit and/or receive data to and/or from the primary receiver unit 104, the data processing terminal 105 or optionally the secondary receiver unit 106.

Also shown in FIG. 1 is an optional secondary receiver unit 106 which is operatively coupled to the communication link and configured to receive data transmitted from the data processing unit 102. The secondary receiver unit 106 may be configured to communicate with the primary receiver unit 104, as well as the data processing terminal 105. The secondary receiver unit 106 may be configured for bi-directional wireless communication with each of the primary receiver unit 104 and the data processing terminal 105. As discussed in further detail below, in certain embodiments the secondary receiver unit 106 may be a de-featured receiver as compared to the primary receiver unit 104, i.e., the secondary receiver unit 106 may include a limited or minimal number of functions and features as compared with the primary receiver unit 104. As such, the secondary receiver unit 106 may include a smaller (in one or more, including all, dimensions), compact housing or embodied in a device such as a wrist watch, arm band, etc., for example. Alternatively, the secondary receiver unit 106 may be configured with the same or substantially similar functions and features as the primary receiver unit 104. The secondary receiver unit 106 may include a docking portion to be mated with a docking cradle unit for placement by, e.g., the bedside for night time monitoring, and/or bi-directional communication device.

Only one sensor 101, data processing unit 102 and data processing terminal 105 are shown in the embodiment of the analyte monitoring system 100 illustrated in FIG. 1. However, it will be appreciated by one of ordinary skill in the art that the analyte monitoring system 100 may include more than one sensor 101 and/or more than one data processing unit 102, and/or more than one data processing terminal 105.

The analyte monitoring system 100 may be a continuous monitoring system, or semi-continuous, or a discrete monitoring system. In a multi-component environment, each component may be configured to be uniquely identified by one or more of the other components in the system so that communication conflict may be readily resolved between the various components within the analyte monitoring system 100. For example, unique IDs, communication channels, and the like, may be used.

In certain embodiments, the sensor 101 is physically positioned in or on the body of a user whose analyte level is being monitored. The sensor 101 may be configured to at least process and send data related to its configuration into a corresponding signal for transmission by the data processing unit 102.

The data processing unit 102 is coupleable to the sensor 101 so that both devices are positioned in or on the user's body, with at least a portion of the analyte sensor 101 positioned transcutaneously. The data processing unit 102 in certain embodiments may include a portion of the sensor 101 (proximal section of the sensor in electrical communication with the data processing unit 102) which is encapsulated within or on the printed circuit board of the data processing unit 102 with, for example, potting material or other protective material. The data processing unit 102 performs data processing functions, where such functions may include but are not limited to, filtering and encoding of data signals, each of which corresponds to a sampled analyte level of the user, for transmission to the primary receiver unit 104 via the communication link 103. In one embodiment, the sensor 101 or the data processing unit 102 or a combined sensor/data processing unit may be wholly implantable under the skin layer of the user.

In one aspect, the primary receiver unit 104 may include an analog interface section including an RF receiver and an antenna that is configured to communicate with the data processing unit 102 via the communication link 103, and a data processing section for processing the received data from the data processing unit 102 such as data decoding, error detection and correction, data clock generation, and/or data bit recovery.

In operation, the primary receiver unit 104 in certain embodiments is configured to synchronize with the data processing unit 102 to uniquely identify the data processing unit 102, based on, for example, identification information of the data processing unit 102, and thereafter, to periodically receive signals transmitted from the data processing unit 102 associated with the monitored analyte levels detected by the sensor 101. That is, when operating in the CGM mode, the receiver unit 104 in certain embodiments is configured to automatically receive data related to the configuration of the sensor from the analyte sensor/sensor electronics when the communication link (e.g., RF range) is maintained or opened between these components.

Referring again to FIG. 1, the data processing terminal 105 may include a personal computer, portable data processing devices or computers such as a laptop computer or a handheld device (e.g., personal digital assistants (PDAs), communication devices such as a cellular phone (e.g., a multimedia and Internet-enabled mobile phone such as an iPhone, a Blackberry device, a Palm device such as Palm Pre, Treo, or similar phone), mp3 player, pager, and the like), drug delivery device, insulin pump, each of which may be configured for data communication with the receiver via a wired or a wireless connection. Additionally, the data processing terminal 105 may further be connected to a data network (not shown).

The data processing terminal 105 may include an infusion device such as an insulin infusion pump or the like, which may be configured to administer insulin to patients, and which may be configured to communicate with the primary receiver unit 104 for receiving, among others, the measured analyte level or configuration data. Alternatively, the primary receiver unit 104 may be configured to integrate an infusion device therein so that the primary receiver unit 104 is configured to administer insulin (or other appropriate drug) therapy to patients, for example, for administering and modifying basal profiles, as well as for determining appropriate boluses for administration based on, among others, the detected analyte levels received from the data processing unit 102. An infusion device may be an external device or an internal device (wholly implantable in a user).

In particular embodiments, the data processing terminal 105, which may include an insulin pump, may be configured to receive the configuration signals from the data processing unit 102, and thus, incorporate the functions of the primary receiver unit 104 including data processing for managing the patient's insulin therapy and analyte monitoring. In certain embodiments, the communication link 103 as well as one or more of the other communication interfaces shown in FIG. 1 may use one or more of an RF communication protocol, an infrared communication protocol, a Bluetooth enabled communication protocol, an 802.11x wireless communication protocol, or an equivalent wireless communication protocol which would allow secure, wireless communication of several units (for example, per HIPPA requirements) while avoiding potential data collision and interference.

As described in aspects of the present disclosure, the analyte monitoring system may include an on-body patch device with a thin profile that can be worn on the arm or other locations on the body (and under clothing worn by the user or the patient), the on-body patch device including an analyte sensor and circuitry and components for operating the sensor and processing and storing signals, including configuration signals, received from the sensor as well as for communication with the reader device. For example, one aspect of the on-body patch device may include electronics to sample the voltage signal received from the analyte sensor in fluid contact with the body fluid, and to process the sampled voltage signals into the corresponding glucose values and/or store the sampled voltage signal as raw data, or to send configuration information as a signal or data.

In certain embodiments, the on-body patch device includes an antenna such as a loop antenna to receive RF power from an external device such as the reader device/receiver unit described above, electronics to convert the RF power received via the antenna into DC (direct current) power for the on-body patch device circuitry, communication module or electronics to detect commands received from the reader device, and communication component to transmit data to the reader device, a low capacity battery for providing power to sensor sampling circuitry (for example, the analog front end circuitry of the on-body patch device in signal communication with the analyte sensor), one or more non-volatile memory or storage devices to store data including raw signals from the sensor or processed data based on the raw sensor signals. More specifically, in the on operation demand mode, the on-body patch device in certain embodiments is configured to transmit real time analyte related data and/or stored historical analyte related data, and/or configuration data when within the RF power range of the reader device. The configuration data can be transmitted prior to transmitting the real time analyte related data.

In certain embodiments, a data processing module/terminal may be provided in the analyte monitoring system that is configured to operate as a data logger, interacting or communicating with the on-body patch device by, for example, transmitting requests for configuration information to the on-body patch device, and storing the responsive configuration information received from the on-body patch device in one or more memory components of the data processing module (e.g., repeater unit). Further, data processing module may be configured as a compact on-body relay device to relay or retransmit the received analyte level information from the on-body patch device to the reader device/receiver unit or the remote terminal or both. The data processing module in one aspect may be physically coupled to the on-body patch device, for example, on a single adhesive patch on the skin surface of the patient. Alternatively, the data processing module may be positioned close to but not in contact with the on-body patch device. For example, when the on-body patch device is positioned on the abdomen of the patient, the data processing module may be worn on a belt of the patient or the user, such that the desired close proximity or predetermined distance of approximately 1-5 inches (or about 1-10 inches, for example, or more) between the on-body patch device and the data processing module may be maintained.

The various processes described above including the processes operating in the software application execution environment in the analyte monitoring system including the on-body patch device, the reader device, data processing module and/or the remote terminal performing one or more routines described above may be embodied as computer programs developed using an object oriented language that allows the modeling of complex systems with modular objects to create abstractions that are representative of real world, physical objects and their interrelationships. The software required to carry out the inventive process, which may be stored in a memory or storage device of the storage unit of the various components of the analyte monitoring system described above in conjunction to the Figures including the on-body patch device, the reader device, the data processing module, various described communication devices, or the remote terminal may be developed by a person of ordinary skill in the art and may include one or more computer program products.

In one embodiment, an apparatus for bi-directional communication with an analyte monitoring system may comprise a storage device having stored therein one or more routines, a processing unit operatively coupled to the storage device and configured to retrieve the stored one or more routines for execution, a data transmission component operatively coupled to the processing unit and configured to transmit data based at least in part on the one or more routines executed by the processing unit, and a data reception component operatively coupled to the processing unit and configured to receive configuration data from a remote location and to store the received configuration data in the storage device for retransmission, wherein the data transmission component is programmed to transmit a query to a remote location, and further wherein the data reception component receives the configuration data from the remote location in response to the transmitted query when one or more electronics in the remote location transitions from an inactive state to an active state upon detection of the query from the data transmission component.

FIG. 2 illustrates a data monitoring and management system for device configuration related data acquisition and processing in one aspect of the present disclosure. More specifically, as shown in FIG. 2, the on-body patch device 211 including sensor electronics coupled to an analyte sensor 250 is positioned on a skin surface 210 of a patient or a user.

Referring back to FIG. 2, as shown, when the reader device/receiver unit 220 is positioned or placed in close proximity and within a predetermined range of the on-body patch device 211, the RF power supply in the reader device/receiver unit 220 may be configured to provide the necessary power to operate the electronics in the on-body patch device 211, and the on-body patch device 211 may be configured to, upon detection of the RF power from the reader device/receiver unit 220, perform preprogrammed routines including, for example, transmitting one or more signals 240 to the reader device/receiver unit 220 indicative of the configuration of the analyte sensor 250.

In certain embodiments, the reader device/receiver unit 220 may include an RF power switch that is user activatable or activated upon positioning within a predetermined distance from the on-body patch device 211 to turn on the analyte sensor in the on-body patch device 211. That is, using the RF signal, the analyte sensor coupled to the sensor electronics in the on-body patch device 211 may be initialized or activated. In another embodiment, a passive RFID function may be provided or programmed such that upon receiving a “turn on” signal which, when authenticated, will turn on the electronic power switch that activates the on-body patch device 211. That is, the passive RFID configuration may include drawing energy from the RF field radiated from the reader device/receiver unit 220 so as to prompt for and/or detect the “turn on” signal which, upon authentication, activates the on-body patch device 211.

In one embodiment, communication and/or RF power transfer between the reader device/receiver unit 220 and the on-body patch device 211 may be automatically initiated when the reader device/receiver unit 220 is placed in close proximity to the on-body patch device 211 as discussed above. Alternatively, the reader device/receiver unit 220 may be configured such that user activation, such as data request initiation and subsequent confirmation by the user using, for example, the display 222 and/or input components 221 of the reader device/receiver unit 220, may be required prior to the initiation of communication and/or RF power transfer between the reader device/receiver unit 220 and the on-body patch device 211. In a further embodiment, the reader device/receiver unit 220 may be user configurable between multiple modes, such that the user may choose whether the communication between the reader device/receiver unit 220 and on-body patch device 211 is performed automatically or requires a user activation and/or confirmation.

As further shown in FIG. 2, the display 222 of the reader device/receiver unit 220 may be configured to provide the functionalities of a user interface to present information such as alarm or alert notification to the user. In one aspect, the reader device/receiver unit 220 may include other output components such as a speaker, vibratory output component and the like to provide audible and/or vibratory output indication to the user in addition to the visual output indication provided on the display 222.

As discussed, some or all of the electronics in the on-body patch device 211 in one embodiment may be configured to rely on the RF power received from the reader device/receiver unit 220 to perform transmission of the configuration information to the reader device/receiver unit 220. That is, the on-body patch device 211 may be discreetly worn on the body of the user or the patient, and under clothing, for example, and when desired, by positioning the reader device/receiver unit 220 within a predetermined distance from the on-body patch device 211, configuration information may be received by the reader device/receiver unit 220.

Referring still to FIG. 2, also shown are a data processing module/terminal 260 and a remote terminal 270. In one aspect, data processing module 260 may include a stand alone device configured for bi-directional communication to communicate with the on-body patch device 211, the reader device/receiver unit 220 and/or the remote terminal 270. More specifically, data processing module 260 may include one or more microprocessors or similar data processing components configured to execute one or more software routines for communication, as well as data storage and retrieval to and from one or more memory components provided in the housing of the data processing module 260.

The data processing module 260 in one embodiment may be configured to communicate with the on-body patch device 211 in a similar manner as the reader device/receiver unit 220 and may include communication components such as antenna, power supply and memory, among others, for example, to allow provision of RF power to the on-body patch device 211 or to request or prompt the on-body patch device 211 to send the configuration data and optionally stored analyte related data. The data processing module 260 may be configured to interact with the on-body patch device 211 in a similar manner as the reader device/receiver unit 220 such that the data processing module 260 may be positioned within a predetermined distance from the on-body patch device 211 for communication with the on-body patch device 211.

In one aspect, the on-body patch device 211 and the data processing module 260 may be positioned on the skin surface of the user or the patient within the predetermined distance of each other (for example, within approximately 5 inches or less) such that the communication between the on-body patch device 211 and the data processing module 260 is maintained. In a further aspect, the housing of the data processing module 260 may be configured to couple to or cooperate with the housing of the on-body patch device 211 such that the two devices are combined or integrated as a single assembly and positioned on the skin surface.

Referring again to FIG. 2, the data processing module 260 may be configured or programmed to prompt or ping the on-body patch device 211 at a predetermined time interval such as upon activation of the on-body patch device 211, or once every five minutes or once every 30 minutes or any other suitable or desired programmable time interval to request configuration data from the on-body patch device 211 which is received and is stored in one or more memory devices or components of the data processing module 260. In another embodiment, the data processing module 260 is configured to prompt or ping the on-body patch device 211 when desired by the patient or the user on-demand, and not based on a predetermined time interval.

As further shown in FIG. 2, the data processing module 260 in one aspect may be configured to transmit the stored data received from the on-body patch device 211 to the reader device/receiver unit 220 when communication between the data processing module 260 and the reader device/receiver unit 220 is established. More specifically, in addition to RF antenna and RF communication components described above, data processing module 260 may include components to communicate using one or more wireless communication protocols such as, for example, but not limited to, infrared (IR) protocol, Bluetooth protocol, Zigbee protocol, and 802.11 wireless LAN protocol. Additional description of communication protocols including those based on Bluetooth protocol and/or Zigbee protocol can be found in U.S. Patent Publication No. 2006/0193375 incorporated herein by reference for all purposes. The data processing module 260 may further include communication ports, drivers or connectors to establish wired communication with one or more of the reader device/receiver unit 220, on-body patch device 211, or the remote terminal 270 including, for example, but not limited to USB connector and/or USB port, Ethernet connector and/or port, FireWire connector and/or port, or RS-232 port and/or connector.

In one aspect, the data processing module 260 may be configured to operate as a data logger configured or programmed to periodically request or prompt the on-body patch device 211 to transmit the configuration information, and to store the received information for later retrieval or subsequent transmission to the reader device/receiver unit 220 or to the remote terminal 270 or both, for further processing and analysis.

In a further aspect, the functionalities of the data processing module 260 may be configured or incorporated into a memory device such as an SD card, microSD card, compact flash card, XD card, Memory Stick card, Memory Stick Duo card, or USB memory stick/device including software programming resident in such devices to execute upon connection to the respective one or more of the on-body patch device 211, the remote terminal 270 or the reader device/receiver unit 220. In a further aspect, the functionalities of the data processing module 260, including executable software and programming, may be provided to a communication device such as a mobile telephone including, for example, iPhone, iPod Touch, Blackberry device, Palm based device (such as Palm Pre, Treo, Treo Pro, Centro), personal digital assistants (PDAs) or any other communication enabled operating system (such as Windows or Android operating systems) based mobile telephones as a downloadable application for execution by the downloading communication device. To this end, the remote terminal 270 as shown in FIG. 2 may include a personal computer, or a server terminal that is configured to provide the executable application software to the one or more of the communication devices described above when communication between the remote terminal 270 and the devices are established.

Depending upon the user setting or configuration on the communication device, the downloaded application may be programmed or customized using the user interface of the respective communication device (screen, keypad, and the like) to establish or program the desired settings such as a receiver alarm, an insulin pump alarm, sensor replacement alarm, or any other alarm or alert conditions as may be desired by the user. Moreover, the programmed notification settings on the communication device may be output using the output components of the respective communication devices, such as speaker, vibratory output component, or visual output/display. As a further example, the communication device may be provided with programming and application software to communicate with the on-body patch device 211 such that a frequency or periodicity of data acquisition is established. In this manner, the communication device may be configured to conveniently receive configuration information from the on-body patch device 211 at predetermined time periods such as, for example, but not limited to during an activation of the on-body patch device 211, once every minute, once every five minutes, or once every 10 or 15 minutes, and store the received information, as well as to provide a desired or appropriate warning indication or notification to the user or the patient.

FIG. 3 is a block diagram of a receiver/monitor unit or insulin pump such as that shown in FIG. 1 in accordance with certain embodiments. The primary receiver unit 104 (FIG. 1) includes one or more of: a blood glucose test strip interface 301, an RF receiver 302, an input 303, a temperature detection section 304, and a clock 305, each of which is operatively coupled to a processing and storage section 307. The primary receiver unit 104 also includes a power supply 306 operatively coupled to a power conversion and monitoring section 308. Further, the power conversion and monitoring section 308 is also coupled to the receiver processor 307. Moreover, also shown are a receiver serial communication section 309, and an output 310, each operatively coupled to the processing and storage unit 307. The receiver may include user input and/or interface components or may be free of user input and/or interface components.

In one aspect, the RF receiver 302 is configured to communicate, via the communication link 103 (FIG. 1) with the data processing unit (sensor electronics) 102, to receive encoded data from the data processing unit 102 for, among others, signal mixing, demodulation, and other data processing. The input 303 of the primary receiver unit 104 is configured to allow the user to enter information into the primary receiver unit 104 as needed. In one aspect, the input 303 may include keys of a keypad, a touch-sensitive screen, and/or a voice-activated input command unit, and the like. The temperature monitor section 304 may be configured to provide temperature information of the primary receiver unit 104 to the processing and control section 307, while the clock 305 provides, among others, real time or clock information to the processing and storage section 307.

Each of the various components of the primary receiver unit 104 shown in FIG. 3 is powered by the power supply 306 (or other power supply) which, in certain embodiments, includes a battery. Furthermore, the power conversion and monitoring section 308 is configured to monitor the power usage by the various components in the primary receiver unit 104 for effective power management and may alert the user, for example, in the event of power usage which renders the primary receiver unit 104 in sub-optimal operating conditions. The serial communication section 309 in the primary receiver unit 104 is configured to provide a bi-directional communication path from the testing and/or manufacturing equipment for, among others, initialization, testing, and configuration determination of the primary receiver unit 104.

Serial communication section 104 can also be used to upload data to a computer, such as configuration data. The communication link with an external device (not shown) can be made, for example, by cable (such as USB or serial cable), infrared (IR) or RF link. The output/display 310 of the primary receiver unit 104 is configured to provide, among others, a graphical user interface (GUI), and may include a liquid crystal display (LCD) for displaying information. Additionally, the output/display 310 may also include an integrated speaker for outputting audible signals as well as to provide vibration output as commonly found in handheld electronic devices, such as mobile telephones, pagers, etc. In certain embodiments, the primary receiver unit 104 also includes an electro-luminescent lamp configured to provide backlighting to the output 310 for output visual display in dark ambient surroundings.

Referring back to FIG. 3, the primary receiver unit 104 may also include a storage section such as a programmable, non-volatile memory device as part of the processor 307, or provided separately in the primary receiver unit 104, operatively coupled to the processor 307. The processor 307 may be configured to perform Manchester decoding (or other protocol(s)) as well as error detection and correction upon the encoded data received from the data processing unit 102 via the communication link 103.

In further embodiments, the data processing unit 102 and/or the primary receiver unit 104 and/or the secondary receiver unit 106, and/or the data processing terminal/infusion section 105 of FIG. 1 may be configured to receive the blood glucose value wirelessly over a communication link from, for example, a blood glucose meter. In further embodiments, a user manipulating or using the analyte monitoring system 100 (FIG. 1) may manually input the blood glucose value using, for example, a user interface (for example, a keyboard, keypad, voice commands, and the like) incorporated in the one or more of the data processing unit 102, the primary receiver unit 104, secondary receiver unit 106, or the data processing terminal/infusion section 105.

Additional detailed descriptions are provided in U.S. Pat. Nos. 5,262,035; 5,264,104; 5,262,305; 5,320,715; 5,593,852; 6,175,752; 6,650,471; 6,746, 582, 6,284,478, 7,299,082, and 7,811,231, in application Ser. No. 11/060,365 filed Feb. 16, 2005 titled “Method and System for Providing Data Communication in Continuous Glucose Monitoring And Management System”, in application Ser. No. 12/698,124 filed Feb. 1, 2010 titled “Compact On-Body Physiological Monitoring Devices and Methods Thereof”, and in application Ser. No. 12/807,278 filed Aug. 31, 2010 titled “Medical Devices and Methods”, each of which is incorporated herein by reference.

Sensors for continuous glucose monitoring systems can be continually improved and these updated versions of the sensors will be made available to consumers. An important consideration for updated sensor products is to ensure that on market system components (e.g., receiver devices, repeater units, glucose meters, insulin pumps, etc.) will work with specific components of the sensor that has been updated. Another consideration is to exclude updated components from operation with certain components if such operation is not safe and effective. For instance, some CGM algorithms may be designed to work with a particular type of sensor but not with others.

In certain embodiments, electronic system update configuration requirements can be enforced using key codes that are incorporated in the communication messages sent between system components. Sensor configuration updates can be managed using a key code technique. Since sensors themselves may not be capable of interacting with other components using key codes, such features may be integrated along with the sensor or sensor delivery system. For instance, in some embodiments, the sensor may provide a radio ID or a resistive code to indicate its configuration to the other system components. The sensor electronics (e.g., transmitter) may use these means to detect the sensor version in order to further manage component configuration (e.g., communicating the sensor version information to other components using key codes). The sensor electronics may have a range of sensor codes that it can accept, or the sensor electronics may pass the sensor code data to the receiver device (or other device in the system) that can have a range of sensor codes that it accepts. Similarly, the transmitter can have a range of acceptable receiver codes and a receiver can have a range of acceptable transmitter codes. In certain embodiments, if the receiver device detects a sensor version that is not allowable or if the transmitter sends the receiver a message indicating that the attached sensor was not allowable, it can notify the user that the sensor version is not allowable. Moreover, the transmitter and/or receiver software can change algorithms or other software functions dependent on the detected software version.

In certain embodiments, key codes can be incorporated in communication messages sent through the devices in the analyte monitoring system. Key codes are primarily available for access by electronic devices. The codes may be used as a book keeping tool to manage which version of the device may function with specific versions of a device application using a particular serial command. For example, a serial command may include a two byte key code that can be issued by a value of code=00 when it sends the command to a device. An original version of a device can be designed with a serial command function that will accept commands with a code range of 00 to 0F, for example. In this manner, if another version of the device has an updated serial command that allows a code range, e.g., of 00 to 1F, then the original device application can still work with the original device, as well as any newer version of the device application that has codes in this range (e.g., specifically to a particular serial command). If an updated devices application is not intended to be compatible with the original device version but only a new device version, then the code for the device application could be set between 10 to 1F. If the updated device is not intended to work with the original device application, then the code for the device can be set to 10 to 1F.

In certain embodiments, the key code mechanism includes a key code communicated in a pairing message exchange between two devices in the analyte monitoring system, in the same manner as described above for device serial commands accessed by a device application. In this case, the key code only needs to be included in a pairing message in order to enforce all communication restrictions between version of the device and the analyte monitoring system, since they may not communicate (e.g., except for pairing attempts) unless they are paired. This aspect can allow for full control over which device versions will work with the analyte monitoring system.

By way of example, in some embodiments, a device could be designed to accept serial commands with names $acona, $aconb, and $aconx, and the device application can issue $aconb. Moreover, the device could be designed to accept a serial command with three parameters and with five parameters.

In other embodiments, a configuration management mechanism is arranged to mechanically key the sensor to only function with a particular transmitter. For example, the sensor electrode contacts may be located in ways to allow some transmitters to properly connect and others to not. Additionally, the sensor can be incorporated into a transmitter mount that mechanically only fits the desired transmitter.

Certain embodiments allow interoperability of various sensor versions with common transmitters and receivers but enforce compatibility requirements at the receiver or other device in the system by requiring that a sensor code be entered prior to glucose calculation and display. The sensor code can be used to define a range of acceptable sensitivity of the device, and may be used to specify the sensitivity itself or contribute to the glucose calculation. Moreover, the sensor may have additional elements that identify the sensor version. Likewise, the sensor code may be used exclusively to identify the sensor version. Then the receiver device can compare the entered sensor code to a list of acceptable codes and if successful, allow glucose calculations or display. Otherwise, the receiver can notify the user that the sensor is not compatible. Furthermore, the receiver software can change algorithms or other software function dependent upon the entered sensor code.

FIG. 4 is a flow diagram illustrating steps in an embodiment for determining the compatibility of a first device 402 in an analyte monitoring system 400. The first device 402 and the second device 404 in the analyte monitoring system 400 can each include at least one of a receiver device, an analyte meter, a glucose monitor, an insulin pump, a continuous analyte monitor, a cellular phone, a personal digital assistant, a personal computer, a laptop computer, and/or a repeater unit. In certain embodiments, a first device 402 sends data related to its configuration to the second device 404 (406). The request can be sent, for example, wirelessly from the transmitter of the first device 402 to the transceiver of the second device 404. The configuration of first device 402, which can be an analyte sensor, can embody one or more various configurations that include different versions of the analyte sensor. Each of the configurations of the first device 402 can include various specifications associated therewith, such as a specific calibration factor and a software function that is used to process analyte data that is obtained by the first device 402. The analyte data can be processed using the software function at the first device 402 or one or more different devices.

Referring still to FIG. 4, the second device 404 receives the data related to the configuration of the first device 402 (408). The second device 404 then retrieves data that is related to configurations that are compatible with the analyte monitoring system 400 (410). The data related to the compatible configurations can be retrieved by the second device 404, for example, from one or more of at least one storage component of the second device 402, an internet based server, from a central server, and/or a distributed server. Next, the second device 404 compares the received data related to the configuration of the first device 402 with the retrieved data that is related to one or more configurations that are compatible with the analyte monitoring system 400 (412). The second device 404 determines if the configuration of the first device 402 is compatible with the analyte monitoring system 400, based upon the comparison of the received data related to the configuration of the first device 402 with the retrieved data related to one or more configurations compatible with analyte monitoring system 400 (414). The second device 404 annunciates or otherwise communicates an alarm to alert a user if it is determined that the first device 402 is not compatible with the analyte monitoring system 400 (416). The alarm may be at least one of an audio alarm, a vibratory alarm, and a visual alarm operatively coupled to the second device 404. If however, the first device 402 is determined to be compatible with the analyte monitoring system 400, then the first device 402 may proceed to obtain analyte data from the user.

FIG. 5 is a flow diagram illustrating steps in an embodiment for determining the compatibility of a first device 502 in an analyte monitoring system 500. The first device 502 and the second device 504 in the analyte monitoring system 500 can each include at least one of a receiver device, an analyte meter, a glucose monitor, an insulin pump, a continuous analyte monitor, a cellular phone, a personal digital assistant, a personal computer, a laptop computer, and/or a repeater unit. In certain embodiments, a first device 502 sends data related to its configuration to the second device 504 (506). The request can be sent, for example, wirelessly from the transmitter of the first device 502 to the transceiver of the second device 504. The configuration of first device 502, which can be an analyte sensor, can embody one or more various configurations that include different versions of the analyte sensor. Each of the configurations of the first device 502 can include various specifications associated therewith, such as a specific calibration factor and a software function that is used to process analyte data that is obtained by the first device 502. The analyte data can be processed using the software function at the first device 502 or one or more different devices.

Referring still to FIG. 5, the second device 504 receives the data related to the configuration of the first device 502 (508). The second device 504 then retrieves data that is related to the configurations the first device 502 may embody that are compatible with the analyte monitoring system 500 (510). The data related to the compatible configurations can be retrieved by the second device 504, for example, from one or more of at least one storage component of the second device 502, an internet based server, from a central server, and/or a distributed server. Next, the second device 504 compares the received data related to the configuration of the first device 502 with the retrieved data that is related to one or more configurations that are compatible with the analyte monitoring system 500 (512). The second device 504 determines if the configuration of the first device 502 is compatible with the analyte monitoring system 500, based upon the comparison of the received data related to the configuration of the first device 502 with the retrieved data related to one or more configurations compatible with analyte monitoring system 500 (514). Following the compatibility determination, the second device 504 communicates, to the first device 502, data related to the compatibility determination to the first device 502 (516). The data can be communicated, for example, from a transmitter of the second device 504 to a transceiver of the first device 502.

Still referring to FIG. 5, the first device 502 receives the data related to its compatibility with the analyte monitoring system 500 from the second device 504 (518) and alerts a user if it was determined by the second device 504 that the first device 502 is not compatible with the analyte monitoring system 500 (520), by annunciating or otherwise communicating an alarm. The alarm may be at least one of an audio alarm, a vibratory alarm, and a visual alarm. If the first device 502 is determined to be compatible with the analyte monitoring system 500, then the first device 502 may proceed to obtain analyte data from the user.

In another embodiment, the compatibility data can be transmitted to and subsequently received by a third device (not shown), and the third device can annunciate or otherwise communicate an alarm to alert the user if the first device 502 is determined to not be compatible with the analyte monitoring system 500.

FIG. 6 is a flow diagram illustrating steps in an embodiment for determining the compatibility of a first device 602 in an analyte monitoring system 600. The first device 602 and the second device 604 in the analyte monitoring system 600 can each include at least one of a receiver device, an analyte meter, a glucose monitor, an insulin pump, a continuous analyte monitor, a cellular phone, a personal digital assistant, a personal computer, a laptop computer, and/or a repeater unit. In certain embodiments, the first device 602 sends data related to its configuration to a second device 604 (606). The data can be sent, for example wirelessly from the transmitter of the first device 602 to the transceiver of the second device 604. The configuration of first device 602, which can be an analyte sensor, can embody one or more various configurations that include different versions of the analyte sensor. Each of the configurations of the first device 602 can include various specifications associated therewith, such as a specific calibration factor and a software function that is used to process analyte data that is obtained by the first device 602. The analyte data can be processed using the software function at the first device 602 or one or more different devices.

Referring still to FIG. 6, the second device 604 receives the data related to the configuration of the first device 602 (608). The second device 604 then retrieves data that is related to one or more compatible configurations of the first device 604 (610). In certain embodiments, the data includes software functions that correlate to the one or more compatible configurations of the first device. The data can be retrieved, for example, from one or more storage components of the second device 602, an internet based server, from a central server, and/or a distributed server. Moreover, the data related to the one or more compatible configurations of the first device 602, and the software functions correlated to the one or more compatible configurations can be stored at the same or separate locations, and can be retrieved at the same time as the compatibility data or at a different time. The second device 604 compares the received data with the retrieved data (612) and determines an appropriate software function that is correlated with the configuration of the first device 602 (614). The software function can be used to process analyte data that is received from the first device 602. The second device 604 receives analyte data that is obtained from the first device 602 (616), which can be sent, for example, wirelessly from the transmitter of the first device 602 to the transceiver of the second device 604. The second device 604 then processes the received analyte data using the determined appropriate software function (618) and displays the processed analyte data to a user (620).

In another embodiment, the second device 604 can communicate data related to the software function associated with the configuration of the first device 602 to a third device (not shown). The analyte data can be communicated from the first device 602 to the third device, and the third device can process the analyte data using the data related to the software function received from the second device 604. The third device may also display the processed analyte data to the user.

In certain embodiments of the present disclosure, a computer-implemented method for determining a compatibility of one or more devices in an analyte monitoring system includes receiving identification code data related to a configuration of a first device, retrieving information including a predetermined list of one or more acceptable identification code data that is related to one or more first device configurations that are compatible with the analyte monitoring system, comparing the received identification code data with the one or more acceptable identification codes from the retrieved predetermined list, and determining if the configuration of the first device is compatible with the analyte monitoring system, based upon the received identification code data being identified in the predetermined list of acceptable identification code data.

Certain aspects include alerting a user if it is determined that the configuration of the first device is not compatible with the analyte monitoring system.

Certain aspects include communicating data related to the determination of the first device being compatible with the analyte monitoring system of a second device.

Certain aspects include the first device communicating the data related to the compatibility of the first device to the second device using at least one key code.

Certain aspects include the data related to the compatibility to the first device communicated using at least one of a radio-identification code or a resistive code or a combination thereof.

Certain aspects include the identification code data including information related to a range of acceptable sensitivity of the first device.

Certain aspects include the identification code data including information related to a version of the first device.

Certain aspects include the user being alerted with at least one of an auditory alarm, a vibratory alarm, and a visual alarm.

Certain aspects include the first device being in fluid contact with an interstitial fluid under a skin layer of a user.

Certain aspects include determining a suitable software function for processing analyte data obtained by the first device, based upon a stored software function that corresponds to the received identification code data, wherein the software function is included in the information related to a predetermined list of one or more acceptable identification code data.

Certain aspects include receiving analyte data obtained by the first device that is related to an analyte level of a user, if it is determined that the first device is compatible with the analyte monitoring system, processing the received analyte data using the determined appropriate software function, and displaying the processed analyte data to the user.

Certain aspects include the compatibility of the first device including a key code of the first device being included in the predetermined list.

Certain aspects include the first device including at least one of a continuous analyte monitor, an analyte sensor, a receiver device, a repeater device, or an insulin pump.

In certain embodiments of the present disclosure, a computer-implemented method for determining a compatibility of one or more devices in an analyte monitoring system includes receiving identification code data related to a configuration of a first device, retrieving information including a predetermined list of one or more identification codes that are related to one or more first device configurations and one or more software functions relating to the one or more first device configurations, comparing the received identification code data with the one or more identification codes, and determining an appropriate software function for processing analyte data obtained by the first device that is related to an analyte level of a user, based upon a stored software function that corresponds to the received identification code data.

Certain aspects include the software function including an algorithm.

Certain aspects include the first device including at least one of a continuous analyte monitor, an analyte sensor, a receiver device, a repeater device, or an insulin pump.

Certain aspects include the information including the predetermined list and the one or more software functions retrieved from at least one of a storage component, an online database, a central database, and a distributed database.

Certain aspects include the information including the predetermined list and the one or more software functions retrieved from different locations.

Various other modifications and alterations in the structure and method of operation of the embodiments of the present disclosure will be apparent to those skilled in the art without departing from the scope and spirit of the present disclosure. Although the present disclosure has been described in connection with certain embodiments, it should be understood that the present disclosure as claimed should not be unduly limited to such embodiments. It is intended that the following claims define the scope of the present disclosure and that structures and methods within the scope of these claims and their equivalents be covered thereby. 

What is claimed is:
 1. A computer-implemented method for determining a compatibility of one or more devices in an analyte monitoring system, comprising: receiving identification code data related to a configuration of a first device; retrieving, using one or more processors, information including a predetermined list of one or more acceptable identification code data that is related to one or more first device configurations that are compatible with the analyte monitoring system; comparing, using the one or more processors, the received identification code data with the one or more acceptable identification codes from the retrieved predetermined list; and determining, using the one or more processors, if the configuration of the first device is compatible with the analyte monitoring system, based upon the received identification code data being identified in the predetermined list of acceptable identification code data.
 2. The computer-implemented method of claim 1, further comprising alerting a user if it is determined that the configuration of the first device is not compatible with the analyte monitoring system.
 3. The computer-implemented method of claim 1, further comprising communicating data related to the determination of the first device being compatible with the analyte monitoring system to a second device.
 4. The computer-implemented method of claim 3, wherein the first device communicates the data related to the compatibility of the first device to the second device using at least one key code.
 5. The computer-implemented method of claim 3, wherein the data related to the compatibility to the first device is communicated using at least one of a radio-identification code and a resistive code.
 6. The computer-implemented method of claim 1, wherein the identification code data includes information related to a range of acceptable sensitivity of the first device.
 7. The computer-implemented method of claim 1, wherein the identification code data includes information related to a version of the first device.
 8. The computer-implemented method of claim 1, wherein the user is alerted with at least one of an auditory alarm, a vibratory alarm, and a visual alarm.
 9. The computer-implemented method of claim 1, wherein the first device is in fluid contact with an interstitial fluid under a skin layer of a user.
 10. The computer-implemented method of claim 1, further comprising determining an appropriate software function for processing analyte data obtained by the first device, based upon a stored software function that corresponds to the received identification code data, wherein the software function is included in the information related to a predetermined list of one or more acceptable identification code data.
 11. The computer-implemented method of claim 10, further comprising: receiving analyte data obtained by the first device that is related to an analyte level of a user, if it is determined that the first device is compatible with the analyte monitoring system; processing, using the one or more processors, the received analyte data using the determined appropriate software function; and displaying, on a display unit, the processed analyte data to the user.
 12. The computer-implemented method of claim 1, wherein the compatibility of the first device includes a key code of the first device being included in the predetermined list.
 13. The computer-implemented method of claim 1, wherein the first device includes at least one of a continuous analyte monitor, an analyte sensor, a receiver device, a repeater device, or an insulin pump.
 14. A computer-implemented method for determining a compatibility of one or more devices in an analyte monitoring system, comprising: receiving identification code data related to a configuration of a first device; retrieving, using one or more processors, information including a predetermined list of one or more identification codes that are related to one or more first device configurations and one or more software functions relating to the one or more first device configurations; comparing, using the one or more processors, the received identification code data with the one or more identification codes; and determining, using the one or more processors, an appropriate software function for processing analyte data obtained by the first device that is related to an analyte level of a user, based upon a stored software function that corresponds to the received identification code data.
 15. The computer-implemented method of claim 14, wherein the software function is an algorithm.
 16. The computer-implemented method of claim 14, wherein the first device includes at least one of a continuous analyte monitor, an analyte sensor, a receiver device, a repeater device, or an insulin pump.
 17. The computer-implemented method of claim 14, wherein the information including the predetermined list and the one or more software functions are retrieved from at least one of a storage component, an online database, a central database, and a distributed database.
 18. The computer-implemented method of claim 17, wherein the information including the predetermined list and the one or more software functions are retrieved from different locations. 